Methods, systems, and computer-readable media for placing orders

ABSTRACT

Included are embodiments for customized ordering. At least one embodiment of a method includes receiving an indication to send a previously created customized order to a vendor and retrieving at least one component of the customized order according to the indication. Some embodiments include determining the vendor associated with the customized order and sending the at least one component of the customized order to the vendor in a first manner, the vendor being configured to receive the customized order.

BACKGROUND

In ordering products and services from vendors, users often are providedwith a plurality of options to customize the order. As such, if a useris ordering the products and/or services online, a plurality of webpages may be presented to the user before the order is complete.Similarly, if a user is placing a telephone order, the user may bepresented with an Interactive Voice Response (IVR) system with aplurality of options and/or may discuss the order with a representativebefore placing the order. While these techniques of placing an order mayprovide convenience in that a user need not drive to a vendor site,place the order, and wait for the goods and/or services, oftentimes theuser repeatedly places the same order with a particular vendor.Regardless, oftentimes, the user must still navigate the same web pages,IVR prompts, and/or representative questions. Such a configuration mayslow the ordering process, as well as incorporate an unnecessary risk oferror in the order.

Thus, a heretofore unaddressed need exists in the industry to addressthe aforementioned deficiencies and inadequacies.

SUMMARY

Included are embodiments for customized ordering. At least oneembodiment of a method includes receiving an indication to send apreviously created customized order to a vendor and retrieving at leastone component of the customized order according to the indication. Someembodiments include determining the vendor associated with thecustomized order and sending the at least one component of thecustomized order to the vendor in a first manner, the vendor beingconfigured to receive the customized order.

Also included are embodiments of a computer readable medium forcustomized ordering. At least one embodiment includes first receivinglogic configured to receive an indication to send a previously createdcustomized order to a vendor and retrieving logic configured to retrieveat least one component of the customized order according to theindication. Some embodiments include first determining logic configuredto determine the vendor associated with the customized order and firstsending logic configured to send the customized order to the vendor in afirst manner, the vendor being configured to receive the customizedorder.

Also included are embodiments of a server for customized ordering. Atleast one embodiment includes a first receiving component configured toreceive an indication to send a previously created customized order to avendor and a retrieving component configured to retrieve at least onecomponent of the customized order according to the indication. Someembodiments include a first determining component configured todetermine the vendor associated with the customized order and a firstsending component configured to send the customized order to the vendorin a first manner, the vendor being configured to receive the customizedorder.

Other systems, methods, features, and advantages of this disclosure willbe or become apparent to one with skill in the art upon examination ofthe following drawings and detailed description. It is intended that allsuch additional systems, methods, features, and advantages be includedwithin this description, be within the scope of the present disclosure.

BRIEF DESCRIPTION

Many aspects of the disclosure can be better understood with referenceto the following drawings. The components in the drawings are notnecessarily to scale, emphasis instead being placed upon clearlyillustrating the principles of the present disclosure. Moreover, in thedrawings, like reference numerals designate corresponding partsthroughout the several views. While several embodiments are described inconnection with these drawings, there is no intent to limit thedisclosure to the embodiment or embodiments disclosed herein. On thecontrary, the intent is to cover all alternatives, modifications, andequivalents.

FIG. 1 is a network diagram illustrating an exemplary embodiment ofcomponents that may be utilized in placing an order with a vendor.

FIG. 2 is a diagram illustrating an exemplary embodiment of componentsthat may be present in a customized order server, such as the customizedorder server from FIG. 1.

FIG. 3 is an exemplary embodiment of a user interface that may bepresented to a user from a vendor's website, such as may be provided bya server from FIG. 1.

FIG. 4 is an exemplary embodiment of a user interface that may bepresented to a user in response to selection of the place order optionfrom FIG. 3.

FIG. 5 is an exemplary embodiment of a user interface that may bepresented to a user in response to selection of the continue option fromFIG. 4.

FIG. 6 is an exemplary embodiment of a user interface that may bepresented to a user in response to selection of the continue option fromFIG. 5.

FIG. 7 is an exemplary embodiment of a user interface that may bepresented to a user in response to selection of the continue option fromFIG. 6.

FIG. 8 is an exemplary embodiment of a user interface that may bepresented to a user in response to selection of the place order optionfrom FIG. 7.

FIG. 9 is an exemplary embodiment of a user interface that may bepresented to a user in response to selection of a view account optionfrom FIG. 3.

FIG. 10 is an exemplary embodiment of a user interface that may bepresented to a user for customized ordering, such as from a user devicefrom FIG. 1.

FIG. 11 is an exemplary embodiment of a user interface that may bepresented to a user in response to receipt of a customized order,similar to the interface from FIG. 10.

FIG. 12 is a flowchart illustrating an exemplary embodiment of a processthat may be utilized for initializing a customized feature, such as inthe network of FIG. 1.

FIG. 13 is a flowchart illustrating an exemplary embodiment of a processthat may be utilized for placing a customized order, similar to theflowchart from FIG. 12.

FIG. 14 is a flowchart illustrating an exemplary embodiment of a processthat may be utilized for capturing data for customized ordering, similarto the flowchart from FIG. 13.

FIG. 15 is a flowchart illustrating an exemplary embodiment of a processthat may be utilized for placing a customized order, similar to theflowchart from FIG. 14.

FIG. 16 is a flowchart illustrating an exemplary embodiment of a processthat may be utilized for sending a customized order in a plurality offormats, similar to the flowchart from FIG. 15.

FIG. 17 is a flowchart illustrating an exemplary embodiment of a processthat may be utilized for initiating customized ordering, similar to theflowchart from FIG. 16.

DETAILED DESCRIPTION

FIG. 1 is a network diagram illustrating an exemplary embodiment ofcomponents that may be utilized in placing an order with a vendor. Asillustrated in the nonlimiting example of FIG. 1, a user can place anorder for products and/or services via a network 100. More specifically,in at least one exemplary embodiment, a user communicating on a userdevice 102 a may place a call to a vendor at a communications device110. In this nonlimiting example, the user can place an order with anemployee at a pizza vendor. Generally speaking, the employee may ask aseries of questions related to the pizza order before the order iscomplete.

Additionally, embodiments of this disclosure also include a user on auser device 102 b placing an order with an online vendor via network100. More specifically, the user may access a website that is providedby a computing device 112, such as a web server. The user can navigate aplurality of web pages provided by the computing device 112 until theorder has been submitted. As indicated above, the user may be asked tonavigate a plurality of web pages each time the user visits the websitebeing provided by the computing device 112. Similarly, a user device 102b may be configured to send a facsimile message to a facsimile machine114 for ordering products and/or services. Similarly, user device 102 cmay be configured to perform one or more of the functions describedabove in a wireless fashion, via communication with an access point 104,cellular tower (not shown) and/or other wireless communication medium.

Additionally included in the nonlimiting example of FIG. 1 are acustomized order server 106 and a data storage component 108. Asdiscussed in more detail below, customized order server 106 may beconfigured to facilitate customized ordering of goods and/or serviceswith the devices 110, 112, 114. More specifically, in at least oneexemplary embodiment, one or more of the user devices 102 a-102 c may beconfigured with customized order options for ordering goods and/orservices from a vendor. As a nonlimiting example, the user device 102 amay be configured to display one or more customized vendors, which maybe defined by the user, the vendor, and/or a provider of the customizedservice. Additionally, some embodiments may be configured to utilizecustomized ordering without utilization of the customized order server106 for at least a portion of the ordering process.

FIG. 2 is a diagram illustrating an exemplary embodiment of componentsthat may be present in a customized order server 106, such as thecustomized order server from FIG. 1. Although a wire-line communicationsdevice is illustrated, this discussion can be applied to wirelessdevices, as well. Generally, in terms of hardware architecture, as shownin FIG. 2, the customized order server 106 includes a processor 282,volatile and nonvolatile memory 284, a display interface 294, datastorage 295, one or more input and/or output (I/O) device interface(s)296, and/or one or more network interfaces 298 that are communicativelycoupled via a local interface 292. The local interface 292 can include,for example but not limited to, one or more buses and/or other wired orwireless connections. The local interface 292 may have additionalelements, which are omitted for simplicity, such as controllers, buffers(caches), drivers, repeaters, and receivers to enable communications.Further, the local interface 292 may include address, control, and/ordata connections to enable appropriate communications among theaforementioned components. The processor 282 may be a device forexecuting software, particularly software stored in volatile andnonvolatile memory 284. The processor 282 can include any custom made orcommercially available processor, a central processing unit (CPU), anauxiliary processor among several processors associated with thecommunications device 106, a semiconductor based microprocessor (in theform of a microchip or chip set), a macroprocessor, and/or generally anydevice for executing software instructions.

The volatile and nonvolatile memory 284 can include any one orcombination of volatile memory elements (e.g., random access memory(RAM, such as DRAM, SRAM, SDRAM, etc.)) and/or nonvolatile memoryelements (e.g., ROM, hard drive, tape, CDROM, etc.). Moreover, thememory 284 may incorporate electronic, magnetic, optical, and/or othertypes of storage media. One should note that the memory 284 can have adistributed architecture (where various components are situated remotefrom one another), but can be accessed by the processor 282.

The software in the memory 284 may include one or more separateprograms, which may include an ordered listing of executableinstructions for implementing logical functions. In the example of FIG.2, the software in the volatile and nonvolatile memory 284 may includecustomized order logic 299, as well as an operating system 286. Theoperating system 286 may be configured to control the execution of othercomputer programs and provides scheduling, input-output control, fileand data management, memory management, and communication control andrelated services.

A system component and/or module embodied as software may also beconstrued as a source program, executable program (object code), script,or any other entity comprising a set of instructions to be performed.When constructed as a source program, the program is translated via acompiler, assembler, interpreter, or the like, which may or may not beincluded within the volatile and nonvolatile memory 284, so as tooperate properly in connection with the operating system 286.

The Input/Output devices that may be coupled to system I/O Interface(s)296 may include input devices, for example but not limited to, akeyboard, mouse, scanner, touch screen, microphone, etc. Further, theInput/Output devices may also include output devices, for example butnot limited to, a printer, display, speaker, etc. Finally, theInput/Output devices may further include devices that communicate bothas inputs and outputs, for instance but not limited to, amodulator/demodulator (modem; for accessing another device, system, ornetwork), a radio frequency (RF) or other transceiver, a telephonicinterface, a bridge, a router, etc.

According to exemplary embodiments, the server 106 includes one or morenetwork interfaces 298 for facilitating communication with one or moreother devices. More specifically, the network interface 298 may includeany component configured to facilitate a connection with another device.While in some embodiments, among others, the customized order server 106can include a network interface 298 that includes a Personal ComputerMemory Card International Association (PCMCIA) card (also abbreviated as“PC card”) for receiving a wireless network card, other configurationscan include the communications hardware within the customized orderserver 106, such that a wireless network card is unnecessary forcommunicating wirelessly. Similarly, other embodiments include networkinterfaces 298 for communicating via a wired connection. Such interfacesmay be configured with Universal Serial Bus (USB) interfaces, serialports, and/or other interfaces.

If customized order server 106 includes a personal computer,workstation, or the like, the software in the volatile and nonvolatilememory 284 may further include a basic input output system (BIOS)(omitted for simplicity). The BIOS is a set of software routines thatinitialize and test hardware at startup, start the operating system 286,and support the transfer of data among the hardware devices. The BIOS isstored in ROM so that the BIOS can be executed when the customized orderserver 106 is activated.

When the customized order server 106 is in operation, the processor 282may be configured to execute software stored within the memory 284, tocommunicate data to and from the memory 284, and to generally controloperations of the customized order server 106 pursuant to the software.Software in the memory 284, in whole or in part, may be read by theprocessor 282, perhaps buffered within the processor 282, and thenexecuted.

One should note that while the description with respect to FIG. 2includes a customized order server 106 as a single component, this is anonlimiting example. More specifically, in at least one embodiment,customized order server 106 can include a plurality of servers, personalcomputers, and/or other devices. Similarly, while the description ofFIG. 2 describes a customized order server 106, this is also anonlimiting example, as other components, such as the user device 102 aand/or other components may also be included in this description.

Additionally, while customized order logic 299 is illustrated in FIG. 2as a single software component, this is also a nonlimiting example. Inat least one embodiment, the customized order logic 299 may include oneor more components, embodied in software, hardware, and/or firmware.Additionally, while customized order logic 299 is depicted as residingon a single computing device, such as customized order server 106,customized order logic 299 may include one or more components residingon one or more different devices.

The embodiments disclosed herein can be implemented in hardware,software, firmware, or a combination thereof. At least one embodimentdisclosed herein is implemented in software and/or firmware that isstored in a memory and that is executed by a suitable instructionexecution system. If implemented in hardware, as in an alternativeembodiment, embodiments disclosed herein can be implemented with any ora combination of the following technologies: a discrete logic circuit(s)having logic gates for implementing logic functions upon data signals,an application specific integrated circuit (ASIC) having appropriatecombinational logic gates, a programmable gate array(s) (PGA), a fieldprogrammable gate array (FPGA), etc.

FIG. 3 is an exemplary embodiment of a user interface 320 that may bepresented to a user from a vendor's website, such as may be provided bya server, such as the computing device 112 from FIG. 1. Morespecifically, the user device, such as the user device 102 b may includebrowser logic for presenting a browser display 300 to the user. Inresponse to instantiating the browser logic (which may be part of thecustomized order logic 299 and/or included as a separate logicalcomponent) and requesting the “Your Pizza Shack” website, the browserlogic may display the browser display 300 and the user interface 320.The user interface 320 can include a place order option 328, a vieworder option 330, and a view account option 332. The place order option328 may be configured to facilitate a user placing an order with thevendor “Your Pizza Shack.” The view order option 330 may be configuredto facilitate presentation of one or more previously placed orders. Theview account option 332 may be configured to facilitate presentation andamendment of the user's account settings.

According to exemplary embodiments, also included in the browser display300 is a customized toolbar 322. The customized toolbar 322 may beassociated with the customized order logic 299 and may be configuredfacilitate capture of data for customized ordering. More specifically,upon instantiating the “Your Pizza Shack” web page, the customized orderlogic 299 can determine whether the vendor Your Pizza Shack isregistered with the customized service. If Your Pizza Shack is notregistered with the customized service, options 326 and 327 may bepresented to the user for starting and stopping data capture for thecustomized service. If Your Pizza Shack is registered with thecustomized service, the options 324 and 326 may be deactivated and theuser can select option 324.

In operation, a vendor may register with the customized order service byreaching an agreement to provide information to the customized orderservice provider for ordering products and/or services. Upon receivingthis data, the customized order service provider may configure thecustomized order server 106 and/or the user device 102 such that theuser's account may be configured for future ordering based on thestructure of Your Pizza Shack's business and/or website model. If, YourPizza Shack is not registered with the customized service, the user maystill utilize the customized capabilities, however the user may selectthe start data capture option 326 to begin a data scrape associated withthe present order. When the user is finished ordering, the user mayselect the stop data capture option 327. Upon receipt of the scrapeddata, the user device 102 and/or the customized order server 106 may beconfigured to determine a technique for facilitating future customizedordering with Your Pizza Shack.

Additionally, if Your Pizza Shack is registered with the customizedservice, the user may select the option 324 to use this order for futurecustomized ordering (thus overriding default and/or previously storedcustomized settings). While in some embodiments options 326, 327 may beutilized at the beginning of the ordering process, option 324 may beutilized at any time during the ordering process.

FIG. 4 is an exemplary embodiment of a user interface 420 that may bepresented to a user in response to selection of the place order option328 from FIG. 3. As illustrated in the nonlimiting example of FIG. 4,the browser display 300 can present the user with the user interface 420for placing an order with the vendor Your Pizza Shack. Morespecifically, the vendor Your Pizza Shack may provide the user with aplurality of options for ordering a pizza. Upon selection of the desiredpizza options, the user can select a continue option 422.

FIG. 5 is an exemplary embodiment of a user interface 520 that may bepresented to a user in response to selection of the continue option 422from FIG. 4. As illustrated in the nonlimiting example of FIG. 5, theuser may further be presented with a plurality of options for orderingother items, such as drinks and sides. Upon selection of the desireddrinks and sides, the user may select a continue option 522.

FIG. 6 is an exemplary embodiment of a user interface 620 that may bepresented to a user in response to selection of the continue option 522from FIG. 5. More specifically, as illustrated in the nonlimitingexample of FIG. 6, the user is prompted to input his or her deliveryinformation, billing information, and payment information. Uponinputting the requested data, the user can select a continue option 622to proceed with the order.

FIG. 7 is an exemplary embodiment of a user interface 720 that may bepresented to a user in response to selection of the continue option 622from FIG. 6. As illustrated in the nonlimiting example of FIG. 7, thebrowser display 300 may be configured to present the user interface 720for confirming the order from FIGS. 3-6. More specifically, data relatedto the order may be presented to the user prior to submitting the order.Upon confirming the order, the user may select a place order option 722.The order may then be submitted to Your Pizza Shack for processing.

FIG. 8 is an exemplary embodiment of a user interface 820 that may bepresented to a user in response to selection of the place order option722 from FIG. 7. As illustrated in the nonlimiting example of FIG. 8,the user interface 820 may be configured to provide the userconfirmation that the order was received and is currently beingprocessed.

As illustrated in the nonlimiting examples of FIGS. 3-8, in the absenceof customized ordering functionality, a user may navigate a plurality ofweb pages before completing the order. While such a configuration mayfacilitate the ordering process, oftentimes, a user desires the sameorder as previously used without having to complete the full orderingprocess.

FIG. 9 is an exemplary embodiment of a user interface 920 that may bepresented to a user in response to selection of the view account option332 from FIG. 3. As illustrated in the nonlimiting example of FIG. 9, auser can view and/or change user information via a change option 922.Additionally, the user can view and/or change customized information viaa change option 924. In this nonlimiting example, the vendor Your PizzaShack is registered with the customized service. As such, the user canset customized ordering options without having to place an order at thistime.

In response to setting and/or changing the customized order options, thevendor communications device 110, the user device, such as the userdevice 102, and/or the customized order server 106 may receive theupdated information for future use. In at least one nonlimiting example,the vendor communications device 110 stores the information, such thatany user device 102 a, 102 b, 102 c, with proper authentication can senda customized signal to place an order according to the customizedoptions. Additionally, some embodiments may be configured such that uponsetting customized options, the user device 102 is configured to receivea customized command and send data related to the customized order. Theuser device 102 may be configured to send the order data to thecustomized order server 106 and/or one or more of the vendor devices110, 112, 114. Similarly, other embodiments can be configured to utilizethe customized order server 106 to receive a customized command from theuser device 102 and send the appropriate order data to one or more ofthe vendor devices 110, 112, 114.

FIG. 10 is an exemplary embodiment of a user interface 1020 that may bepresented to a user for customized ordering, such as from the userdevice 102 b from FIG. 1. As illustrated in the nonlimiting example ofFIG. 10, the user interface 1020 may be presented via the user device102 b, which may include a personal computer, cellular telephone, aBellSouth® Personal Device top (BPD), a Quickconnect™ device, a KitchenBroadband Device (KBD), other general purpose device, and/or otherspecific purpose device configured for facilitating customized ordering.

The user interface 1020 may be configured to display one or moreselectable options associated with customized ordering. Morespecifically, the nonlimiting example of the user interface 1020 isconfigured to display selectable options 1022 a-1022 h, which, accordingto exemplary embodiments, include names of vendors that are registeredwith the ordering service described herein. Upon selection of one ormore of the options 1022, an order may be automatically placed with theselected vendor. Additionally, scroll options 1024 a, 1024 b may beconfigured to view additional customized vendors associated with theuser. Additionally, the user interface 1020 may also include an optionfor adding additional vendors to the customized vendor list of the userinterface 1020. By selecting an add more option 1026, the user may bepresented with an option to designate an additional vendor and/or anoption to designate the customized order for this vendor.

Similarly, the user interface 1020 may also include a change existingoption 1028 for changing the display order of vendors in the userinterface 1020, changing the display name of the vendors of the userinterface 1020, changing the order associated with the customized orderoptions and/or changing other portions of the customized orderingconfiguration. Additionally, one or more vendors may be removed from theuser interface 1020 by selecting a delete option 1030.

One should note that, while the description above relates to orderingfrom the vendor Your Pizza Shack, this is a nonlimiting example. Morespecifically, as illustrated in FIG. 10, customized ordering can beapplied to any of a plurality of different vendors. Additionally,depending on the particular configuration, a vendor may be listed as aplurality of customized ordering options. More specifically, in at leastone exemplary embodiment, El Guapo Mexican Restaurant may be listedtwice (under the same name or different names). A first occurrence ofthis vendor can include a customized order option for a first order anda second occurrence can include a customized order option for a secondorder with this vendor.

FIG. 11 is an exemplary embodiment of a user interface 1120 that may bepresented to a user in response to receipt of a customized order,similar to the interface 1020 from FIG. 10. As illustrated in thenonlimiting example of FIG. 11, in response to selecting one of thecustomized order option 1022 a-1022 h from FIG. 10, the user interface1120 may be displayed, confirming the order. According to exemplaryembodiments, the order displayed includes an order provided by aparticular vendor and selected by the user to be associated with theordering service described herein. For example, if a user consistentlyorders a 12 inch hand tossed pepperoni pizza, a 2-liter bottle of brownsoda, and an order of breadsticks from the vendor Your Pizza Shack, thenthe user may decide to associate the order with the ordering service sothat when the user selects the ordering option 1022 a, the orderincluding the pizza, bottle of soda and breadsticks is retrieved fororder confirmation, as illustrated in FIG. 11, eliminating the need forthe user step through a number of options to achieve the same order. Ifthe user wishes to change the order, the user may select a change option1122 to be presented with options for changing the order. If the userwishes to cancel the order, the user can select a cancel option 1124.

One should note that, depending on the particular configuration, theuser may be presented with a intermediate user interface (not shown) toconfirm that the order is being processed (similar to the user interface720, from FIG. 7). Additionally, the user interface 1120 may also beconfigured to display a countdown for the expected delivery of theorder. Similarly, some embodiments may be configured to display acurrent status and/or position of the order. As a nonlimiting example,referring back to a previous example, if the user orders a pizza fromthe vendor Your Pizza Shack, the user interface 1120 may be configuredto determine (from the vendor computing device 112 and/or from othersources) whether the pizza is currently in the oven. If the pizza is outof the oven, the user interface 1120 may be configured to determinewhether the order is currently in transit and, if so, the geographicalposition of the order.

FIG. 12 is a flowchart illustrating an exemplary embodiment of a processthat may be utilized for initializing a customized feature, such as inthe network of FIG. 1. As illustrated in the nonlimiting example of FIG.12, a user can instantiate a browser (block 1232) associated with a userdevice, such as the user device 102 b. The user can then navigate thebrowser to a desired website (block 1234). The user can select the startdata capture option 326 (block 1236). The browser can then begin tocapture data sent to and/or received from one or more websites that theuser is browsing (block 1238). The user can then navigate one or moreweb pages during the purchase of goods and/or services (block 1240). Theuser can select the stop data capture option 327 (block 1242). Thebrowser can stop data capture and send the captured data to thecustomized order server 106 (block 1244). The customized order server106 can process the received data to determine whether customizedordering is plausible. Customized ordering may be plausible when theuser has an account that is configured for customized ordering and/or inother scenarios. If customized ordering is plausible, the customizedorder server 106 determines data, such as ordering preferences, etc.,which may be associated with a code that uniquely identifies the userthat is associated with the order for future customized ordering.Additionally, the server 106 stores the determined data (block 1246).

One should note that the nonlimiting example described with reference toFIG. 12 illustrates an exemplary embodiment associated with customizedordering when the vendor is not registered with the customized service.Additionally, depending on the particular configuration, a similarprocess may be utilized, regardless of whether the vendor is registered.One should also note that in at least one exemplary embodiment the userdevice 102 is configured to process the captured data to determinefuture customized ordering procedures (e.g., blocks 1244, 1246).

FIG. 13 is a flowchart illustrating an exemplary embodiment of a processthat may be utilized for placing a customized order, similar to theflowchart from FIG. 12. As illustrated in the nonlimiting example ofFIG. 13, a user may select a customized order option on a user device102 (block 1332). The user device 102 can send an order request to thecustomized order server 106 (block 1334). The customized order server106 can determine the order associated with the order request and senddata associated with the order to the designated vendor (block 1336). Adetermination can then be made as to whether the order request isaccepted by the vendor (block 1338). If the order request is notaccepted (e.g., the vendor is not currently open, the vendor is nottaking orders at this time, the customer has a past due balance, etc.),the customized order server 106 can determine the problem with the orderrequest (block 1340). The customized order server 106 can then send anerror message to the user device 102 (block 1342). If, at block 1338,the request is accepted, the vendor can send confirmation to thecustomized order server 106 (block 1344). The customized order server106 can then send confirmation to the user device 102 (block 1346). Asnoted above, by using the order service described herein, the user mayreduce the number of steps required to provide an order to a vendor.

FIG. 14 is a flowchart illustrating an exemplary embodiment of a processthat may be utilized for capturing data for customized ordering, similarto the flowchart from FIG. 13. As illustrated in the nonlimiting exampleof FIG. 14, a user can navigate a website associated with a vendor(block 1432). The user can select the start data capture option 266(block 1434). The browser can send an indication to the customized orderserver 106 (block 1436). The customized order server 106 can thendetermine whether there is an established agreement between thecustomized order service provider and the vendor (block 1438). If thereis no established agreement, the customized order server 106 can collectdata communicated between the user's browser and the vendor (block1440). The customized can then associate the retrieved data with theuser and store the retrieved data (block 1442).

If, at block 1438, the customized order server 106 determines that thereis an established agreement, the customized order server 106 candetermine data requested by this vendor to facilitate customizedordering (block 1444). The customized order server 106 can then storethe requested data as communicated between the user and vendor until theuser selects stop data capture option 267 (block 1446).

One should note that, while the nonlimiting example of FIG. 14illustrates that a determination can be made in response to selection ofthe start data capture option 266, this is a nonlimiting example. Morespecifically, in at least one exemplary embodiment, the customized orderlogic 299 may be configured to determine whether the vendor has anagreement with the customized order service provider upon the useraccessing the vendor's website. Additionally, some embodiments may beconfigured to operate without utilizing the customized order server 106.

FIG. 15 is a flowchart illustrating an exemplary embodiment of a processthat may be utilized for placing a customized order, similar to theflowchart from FIG. 14. As illustrated in the nonlimiting example ofFIG. 15, a user can select a customized order option on user device 102(block 1532). The user device 102 can determine the vendor and/or orderthat was selected (block 1534). A determination can then be made as towhether an agreement exists between the vendor and the customized orderservice provider (block 1536). If no agreement exists, the customizedorder logic 299 (which may be associated with the user device 102 and/orcustomized order server 106) can navigate the vendor website to placeorder (block 1538). One should note that the customized order logic 299can navigate the vendor website according to previously captured dataassociated with this vendor. Additionally, while the exemplaryembodiment of FIG. 15 discusses navigating a website, this is also anonlimiting example, as some embodiments may be configured to send afacsimile to the vendor and/or place a telephone call with the vendor toplace the order. Such configurations may utilize text-to-speechconversion techniques and/or other translation logic for converting theorder into the desired format.

Upon placing the order, a determination can be made as to whether thereis an error associated with the placed order (block 1540). If there isan error, the customized order server 106 can receive an error messagefrom the vendor (block 1542). The customized order server 106 can thensend the error message to the user device 102 (block 1544). If, at block1540, there is not an error associated with the order, the flowchart canproceed to block 1548, discussed below.

If, at block 1536, a determination is made that an agreement existsbetween the vendor and the customized order service provider, thecustomized order server 106 can submit order data as requested by thevendor (block 1546). The customized order server 106 can then receive anorder confirmation (block 1548). The customized order server 106 canthen send the order confirmation to the user device 102 (block 1550).

FIG. 16 is a flowchart illustrating an exemplary embodiment of a processthat may be utilized for sending a customized order in a plurality offormats, similar to the flowchart from FIG. 15. As illustrated in thenonlimiting example of FIG. 16, the customized order server 106 canreceive an order for a vendor (block 1632). The customized order server106 can send the order data to the vendor in a first manner (block1634). The first manner can include any of a plurality of techniques,including navigating the vendor's website, determining whether thevendor has an agreement with the customized order service provider,sending a facsimile message, placing a telephone call, etc. In responseto sending the order data in a first manner, the customized order server106 can receive an error message indicating that the order was notprocessed (block 1636). The customized order server 106 can then send anerror message to the user device 102 (block 1638). The customized orderserver 106 can then send the order data in a second manner (block 1640).Sending the order data in a second manner can include sending the orderdata in a different manner than the first manner. More specifically, asa nonlimiting example, if the customized order server 106 firstnavigates the website, the customized order server 106 can send afacsimile message as the second manner. The customized order server 106can then receive a confirmation message indicating that the order isbeing processed (block 1642). The customized order server 106 can thensend the substance of the confirmation message to the user device 102(block 1644).

One should note that while the nonlimiting example of FIG. 16illustrates an exemplary embodiment where sending the order data in afirst manner receives an error message, this is a nonlimiting example,used for illustration purposes only. More specifically, in at least oneexemplary embodiment, the order data may be sent in a first manner andthen a determination is made as to whether the order is processed. Ifthe order is not processed, the customized order server 106 may send theorder data in a second manner. If the order is processed, the customizedorder server 106 may proceed as in blocks 1642 and 1644. Similarly,while the nonlimiting example of FIG. 16 illustrates sending the orderdata in a first manner and a second manner, one should note that thecustomized order server 106 may send the order data in any number ofdifferent manners until the order is processed. Additionally, thecustomized order server 106 may also send the order data in a firstmanner (or second manner, etc.) any number of times until the order isprocessed.

FIG. 17 is a flowchart illustrating an exemplary embodiment of a processthat may be utilized for initiating customized ordering, similar to theflowchart from FIG. 16. As illustrated in the nonlimiting example ofFIG. 17, a user device 102 displays default customized order options(block 1732). More specifically, depending on the vendors that thecustomized order service provider has obtained agreements, a defaultlisting of vendors may be displayed when the user device 102 is firstused. The user can then select at least one of the customized orderoptions (block 1734). The user device may then contact the vendorassociated with the selected option to set up customized ordering (block1736). As discussed above, in some embodiments, the user device 102 maybe configured to directly contact the vendor. Similarly, someembodiments may be configured such that the user device 102 contacts thecustomized order server 106, which then communicates with the vendor.Upon setting up the customized order options for ordering with the user,the vendor can then send the preferences to the customized order server106 (block 1738). The customized order server can then send thepreference data to the user device 102 (block 1740).

The embodiments disclosed herein can be implemented in hardware,software, firmware, or a combination thereof. At least one embodiment,disclosed herein is implemented in software and/or firmware that isstored in a memory and that is executed by a suitable instructionexecution system. If implemented in hardware, as in an alternativeembodiment embodiments disclosed herein can be implemented with any or acombination of the following technologies: a discrete logic circuit(s)having logic gates for implementing logic functions upon data signals,an application specific integrated circuit (ASIC) having appropriatecombinational logic gates, a programmable gate array(s) (PGA), a fieldprogrammable gate array (FPGA), etc.

One should note that the flowcharts included herein show thearchitecture, functionality, and operation of a possible implementationof software. In this regard, each block can be interpreted to representa module, segment, or portion of code, which comprises one or moreexecutable instructions for implementing the specified logicalfunction(s). It should also be noted that in some alternativeimplementations, the functions noted in the blocks may occur out of theorder and/or not at all. For example, two blocks shown in succession mayin fact be executed substantially concurrently or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved.

One should note that any of the programs listed herein, which caninclude an ordered listing of executable instructions for implementinglogical functions, can be embodied in any computer-readable medium foruse by or in connection with an instruction execution system, apparatus,or device, such as a computer-based system, processor-containing system,or other system that can fetch the instructions from the instructionexecution system, apparatus, or device and execute the instructions. Inthe context of this document, a “computer-readable medium” can be anymeans that can contain, store, communicate, or transport the program foruse by or in connection with the instruction execution system,apparatus, or device. The computer readable medium can be, for examplebut not limited to, an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor system, apparatus, or device. More specificexamples (a nonexhaustive list) of the computer-readable medium couldinclude an electrical connection (electronic) having one or more wires,a portable computer diskette (magnetic), a random access memory (RAM)(electronic), a read-only memory (ROM) (electronic), an erasableprogrammable read-only memory (EPROM or Flash memory) (electronic), anoptical fiber (optical), and a portable compact disc read-only memory(CDROM) (optical). In addition, the scope of the certain embodiments ofthis disclosure can include embodying the functionality described inlogic embodied in hardware or software-configured mediums.

One should also note that conditional language, such as, among others,“can,” “could,” “might,” or “may,” unless specifically stated otherwise,or otherwise understood within the context as used, is generallyintended to convey that certain embodiments include, while otherembodiments do not include, certain features, elements and/or steps.Thus, such conditional language is not generally intended to imply thatfeatures, elements and/or steps are in any way required for one or moreparticular embodiments or that one or more particular embodimentsnecessarily include logic for deciding, with or without user input orprompting, whether these features, elements and/or steps are included orare to be performed in any particular embodiment.

It should be emphasized that the above-described embodiments are merelypossible examples of implementations, merely set forth for a clearunderstanding of the principles of this disclosure. Many variations andmodifications may be made to the above-described embodiment(s) withoutdeparting substantially from the spirit and principles of thedisclosure. All such modifications and variations are intended to beincluded herein within the scope of this disclosure.

1. A method for customized ordering, comprising: receiving, by at leastone computer, browser captured data corresponding to an order submittedby the user to a vendor and saving order details within the browsercaptured data as a previously created customized order; subsequentlyreceiving, by the at least one computer, an indication to send thepreviously created customized order to the vendor; retrieving, by the atleast one computer, at least one component of the previously createdcustomized order according to the indication; determining, by the atleast one computer, the vendor associated with the previously createdcustomized order; and sending, by the at least one computer, the atleast one component of the previously created customized order to thevendor in a first manner, the vendor being configured to receive thepreviously created customized order.
 2. The method of claim 1, furthercomprising determining whether the vendor has established an agreementwith a customized order service provider.
 3. The method of claim 2,further comprising, in response to determining that the vendor hasestablished an agreement with the customized order service provider,determining a format for sending the previously created customized orderto the customized order service provider.
 4. The method of claim 2,further comprising, in response to determining that the vendor has notestablished an agreement with the customized order service provider,navigating a website associated with the vendor to place the previouslycreated customized order.
 5. The method of claim 1, further comprising:determining whether the previously created customized order isprocessed; in response to determining that the previously createdcustomized order has been processed, receiving a confirmation; andsending at least a portion of the confirmation to a user device thatsent the indication to place the previously created customized order. 6.The method of claim 1, further comprising: determining whether thepreviously created customized order is processed; in response todetermining that the previously created customized order has not beenprocessed, determining a second manner to send the previously createdcustomized order; and sending the previously created customized order inthe determined second manner.
 7. The method of claim 6, wherein sendingthe previously created customized order in a first manner includes atleast one of the following: sending the previously created customizedorder in a format associated with the vendor, navigating a websiteassociated with the vendor, sending a facsimile message, and placing atelephone call, wherein sending the previously created customized orderin a second manner includes at least one of the following: sending thepreviously created customized order in a format associated with thevendor, navigating a website associated with the vendor, sending afacsimile message, and placing a telephone call, and wherein the firstmanner is different than the second manner.
 8. A non-transitory computerreadable medium for customized ordering, comprising: first receivinglogic configured to receive browser captured data corresponding to anorder submitted by the user to a vendor and saving order details withinthe browser captured data as a previously created customized order;second receiving logic configured to subsequently receive an indicationto send the previously created customized order to the vendor;retrieving logic configured to retrieve at least one component of thepreviously created customized order according to the indication; firstdetermining logic configured to determine the vendor associated with thepreviously created customized order; and first sending logic configuredto send the previously created customized order to the vendor in a firstmanner, the vendor being configured to receive the previously createdcustomized order.
 9. The non-transitory computer readable medium ofclaim 8, further comprising second determining logic configured todetermine whether the vendor has established an agreement with acustomized order service provider.
 10. The non-transitory computerreadable medium of claim 9, further comprising, third determining logicconfigured to, in response to the second determining logic determiningthat the vendor has established an agreement with the customized orderservice provider, determine a format for sending the previously createdcustomized order to the customized order service provider.
 11. Thenon-transitory computer readable medium of claim 9, further comprising,navigating logic configured to, in response to determining that thevendor has not established an agreement with the customized orderservice provider, navigate a website associated with the vendor to placethe previously created customized order.
 12. The non-transitory computerreadable medium of claim 8, further comprising: fourth determining logicconfigured to determine whether the previously created customized orderis processed; third receiving logic configured to, in response todetermining that the previously created customized order has beenprocessed, receive a confirmation; and second sending logic configuredto send at least a portion of the confirmation to a user device thatsent the indication to place the previously created customized order.13. The non-transitory computer readable medium of claim 8, furthercomprising: fifth determining logic configured to determine whether thepreviously created customized order is processed; sixth determininglogic configured to, in response to determining that the previouslycreated customized order has not been processed, determine a secondmanner to send the previously created customized order; and thirdsending logic configured to send the previously created customized orderin the determined second manner.
 14. The non-transitory computerreadable medium of claim 13, wherein sending the previously createdcustomized order in a first manner includes at least one of thefollowing: sending the previously created customized order in a formatassociated with the vendor, navigating a website associated with thevendor, sending a facsimile message, and placing a telephone call,wherein sending the previously created customized order in a secondmanner includes at least one of the following: sending the previouslycreated customized order in a format associated with the vendor,navigating a website associated with the vendor, sending a facsimilemessage, and placing a telephone call, and wherein the first manner isdifferent than the second manner.
 15. A server for customized ordering,comprising: a first receiving component configured to receive browsercaptured data corresponding to an order submitted by the user to avendor and saving order details within the browser captured data as apreviously created customized order; a second receiving componentconfigured to subsequently receive an indication to send the previouslycreated customized order to the vendor; a retrieving componentconfigured to retrieve at least one component of the previously createdcustomized order according to the indication; a first determiningcomponent configured to determine the vendor associated with thepreviously created customized order; and a first sending componentconfigured to send the previously created customized order to the vendorin a first manner, the vendor being configured to receive the previouslycreated customized order.
 16. The server of claim 15, further comprisinga second determining component configured to determine whether thevendor has established an agreement with a customized order serviceprovider.
 17. The server of claim 16, further comprising, a thirddetermining component configured to, in response to the seconddetermining component determining that the vendor has established anagreement with the customized order service provider, determine a formatfor sending the previously created customized order to the customizedorder service provider.
 18. The server of claim 16, further comprising,a navigating component configured to, in response to determining thatthe vendor has not established an agreement with the customized orderservice provider, navigate a website associated with the vendor to placethe previously created customized order.
 19. The server of claim 15,further comprising: a fourth determining component configured todetermine whether the previously created customized order is processed;a third receiving component configured to, in response to determiningthat the previously created customized order has been processed, receivea confirmation; and a second sending component configured to send atleast a portion of the confirmation to a user device that sent theindication to place the previously created customized order.
 20. Theserver of claim 15, further comprising: a fifth determining componentconfigured to determine whether the previously created customized orderis processed; a sixth determining component configured to, in responseto determining that the previously created customized order has not beenprocessed, determine a second manner to send the previously createdcustomized order; and a third sending component configured to send thepreviously created customized order in the determined second manner.